Records the assessment (from the operator's question) of how likely
bardioc — arago's HIRO/Bardioc engine, the original OGIT authors —
discovered the "semantic compiler" superpowers OGAR articulates.

Verdict, reasoning purely from the OGIT artifact (NTO + SGO + MARS XSD
+ extract_classes.py), not insider history: HIGH likelihood they
discovered and exploited it operationally; LOW likelihood they framed
it as a compiler. They built a semantic compiler and described it in
Semantic-Web vocabulary (rdfs:/owl:/dcterms:), not compiler vocabulary.

The discipline is the tell ([G], visible in files): SGO verbs as a
symbol table with ogit:from-to typed signatures; validation-type
"fixed" as a closed-enum type system; mandatory/optional/indexed
cardinality; ogit:allowed as capability declaration; NTO/SGO scope
layering; MARS A→R→S→M dependency DAG; extract_classes.py as a codegen
back-end; OGIT-as-canonical-source consumed by HIRO.

Sharpest evidence: OGIT carries ONLY the structural arm; behaviour
lived in HIRO (Elixir gen_statem). That separation IS the
structural/behavioural-arm split this workspace "rediscovered."

On OGAR-AS-IR's six IR-shape tests OGIT satisfies ~3/6 (typed-signature,
IR-canonical, named-lowering partial; missing effect-annotations, SSA,
semantic-preservation guarantee) — "a disciplined structural IR with
the behavioural half externalized."

What bardioc did NOT do — and OGAR's actual contribution — is the
UNIFICATION (two arms of one IR; structural lowers to N back-ends;
behavioural stays in Core; same address resolves both). OGAR renames
what bardioc built (compiler vocabulary) and unifies the two halves
they kept apart, NOT the underlying discovery.

Honest external-framing consequence: credit bardioc's structural
discipline; OGAR contributes the IR unification + compiler framing.
This is accurate AND strengthens the claim (battle-tested substrate).

Graded fences: [G] shape exhibits compiler properties; [H] bardioc
consciously knew; [S] they had the full IR-discipline (falsified by
the 3/6 profile — the unification is genuinely OGAR's).

…uth symbol table (external-IAM bridge)

Addendum to the semantic-compiler thesis (prior commit c0e872e),
prompted by the operator's observation that arago recently expanded
the Auth domain — probably unifying with their Zitadel auth server.

Verified from NTO/Auth dcterms:valid dates:

* The IAM core is arago's own, 2018 (Organization, OrgDomain, Account,
  Application, Role, RoleAssignment, Team, DataScope) — PREDATES
  Zitadel's prominence (~2020-2022), so convergent-universal-IAM, not
  copied.
* A January 2026 batch by Pablo Perez adds foreign-key-shaped IDs —
  organizationId/accountId/applicationId/scopeId/configurationData
  (all 2026-01-12) + ApplicationContent (2026-01-14) — hanging off a
  Configuration entity ("registered in hiro knowledge core",
  belongs Organization).

The tell ([H], pattern not a named string): adding FK ID columns is
what you do to bridge to an EXTERNAL system keyed by those identities.
The config blob lives in HIRO, keyed by the external IAM's
org/app/user/scope IDs. Zitadel is most likely (its
org_id/project_id/app_id/user_id are exactly these four FK shapes;
matches the operator's stack) but no file names it — hence [H].
Caveat: the domain also carries a Zanzibar-relation shape (edgeRule/
vertexRule + membership verbs), positioned to host Zitadel AND Ory/Keto
bindings — matching the operator's "preminted class profiles" framing.

Two consequences logged: (1) strengthens the semantic-compiler thesis
with a LIVE receipt — the linker phase (OGAR-AS-IR §1) is actively in
use in 2026, not a fossil; (2) the Configuration-keyed-by-external-IDs
entity is the OGIT-side precedent for the "AuthStore mapping class" and
informs the queued 0x0BXX auth cross-walk.

No code changes; ledger entry only. Joins PR #109 (same open branch).